
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
Third-party components and deployment</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="apptechp245.htm">Previous</A>&nbsp;&nbsp;<A HREF="apptechp247.htm" >Next</A>
<!-- End Header -->
<A NAME="CHDHHJGD"></A><h1>Third-party components and deployment</h1>
<A NAME="TI6856"></A><p>PowerBuilder applications have some dependencies on third-party components
that are installed with PowerBuilder. Most of these components are <i>not</i> installed
with the PowerBuilder Runtime Packager. You may redistribute some
of these components with your application, but others must be obtained
from the vendor.</p>
<A NAME="TI6857"></A><p>For information about components that can be freely downloaded,
see the free download terms document. A copy of this document is
located in the <i>Support</i> directory on the DVD
and on <A HREF="http://www.sybase.com/softwarelicenses/third_party_legal">the Sybase Web site</A>
.</p>
<A NAME="BABIFDFJ"></A><h2>Apache files</h2>
<A NAME="TI6858"></A><p>You may redistribute Apache files included with PowerBuilder
to your users. Any use or distribution of the Apache code included
with PowerBuilder 11.5 must comply with the terms of the Apache
License which is located in the free download terms document for
PowerBuilder 11.5.</p>
<A NAME="TI6859"></A><p>Version 0.20.4 of the Apache Formatting Objects Processor
(FOP) is required if your application uses XSL-FO to save files
as PDF. For more information about FOP, see <A HREF="http://xmlgraphics.apache.org/fop/">the Apache FOP Web site</A>
. </p>
<A NAME="TI6860"></A><p>The Apache Xerces files <i>xerces-c_2_6.dll</i> and <i>xerces-depdom_2_6.dll</i> are required
for XML Web DataWindow support, XML support for DataWindows and DataStores,
PBDOM, and SOAP clients for Web services. For more information about Xerces,
see <A HREF="http://xml.apache.org/xerces-c/">the Xerces C++ Parser Web site</A>
.</p>
<A NAME="BABCJHBA"></A><h2>Microsoft files</h2>
<A NAME="TI6861"></A><h4>Visual C++ runtime, Active
Template, and GDI+ libraries</h4>
<A NAME="TI6862"></A><p>When you deploy the core PowerBuilder runtime files, you must
ensure that the <i>msvcr71.dll</i> and <i>msvcp71.dll</i> Microsoft
Visual C++ runtime libraries and the Microsoft
.NET Active Template Library (ATL) module, <i>atl71.dll</i>,
are present on the user's computer or server. The PowerBuilder
runtime files have a runtime dependency on these files and they
are required for all applications and components that require the
PowerBuilder runtime. You can obtain these DLL files from the <A HREF="http://dlldump.com">DLL archive Web site</A>
.
They are also available from the <A HREF="http://driverskit.com">DLL archive Web site</A>
.</p>
<A NAME="TI6863"></A><p>The PowerBuilder runtime files also have a runtime dependency
on Microsoft Windows GDI+ (<i>gdiplus.dll</i>).
PowerBuilder .NET targets cannot be launched if <i>gdiplus.dll</i> is
not available on the system. GDI+ is the subsystem of the Windows
XP or Windows Server 2003 operating system that implements enhanced
graphic capabilities for screens and printers. It is included with Windows
Vista but it is not part of the Windows 2000 operating system, therefore
if you deploy your PowerBuilder application to Windows 2000, you must
make sure that <i>gdiplus.dll</i> is available on
the target computer and in the system path. GDI+ can be
downloaded from the <A HREF="http://www.microsoft.com/downloads/details.aspx?FamilyID=6A63AB9C-DF12-4D41-933C-BE590FEAA05A&amp;displaylang=en">Microsoft Web site</A>
.</p>
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Files must be installed before running MSI file</span> <A NAME="TI6864"></A>Some files installed by the MSI file generated by the PowerBuilder
Runtime Packager have dependencies on these files. For example, <i>atl71.dll</i> and <i>gdiplus.dll</i> must
be installed on the user's computer before the <i>pbjvm115.dll</i> file
can be registered. Make sure these files are on the target computer
before you run the MSI file generated by the Runtime Packager.</p>
<A NAME="TI6865"></A><h4>Ink picture libraries</h4>
<A NAME="TI6866"></A><p><i>Microsoft.Ink</i>, <i>Microsoft.Ink.dll</i>,
and <i>Microsoft.Resources.dll</i> are required if your
application uses InkEdit and InkPicture controls. These files are
part of the Microsoft Windows XP Tablet PC Edition Software Development
Kit 1.7, which is available on the <A HREF="http://www.microsoft.com/downloads/details.aspx?FamilyId=B46D4B83-A821-40BC-AA85-C9EE3D6E9699&amp;displaylang=en">Microsoft Web site</A>
. </p>
<A NAME="TI6867"></A><p>Microsoft has discovered some incompatibility issues between
these DLLs and the .NET Framework 2.0. You can obtain an update
to address these issues from <A HREF="http://www.microsoft.com/downloads/details.aspx?familyid= 84BBEFA4-7047-41DF-8583-E3BDBF9D805F&amp;displaylang=en">Microsoft</A>
.</p>
<A NAME="TI6868"></A><h4>DirectX runtime</h4>
<A NAME="TI6869"></A><p>PowerBuilder applications can use DirectX 3D rendering to
display 3D graphs (Pie3D, Bar3D, Column3D, Line3D, and Area3D) with
a more sophisticated look. You can use data item or series transparency
with the DirectX graph styles to improve the presentation of data. </p>
<A NAME="TI6870"></A><p>The DirectX 3D rendering depends on the DirectX runtime. The
first time you select the Render3D check box on the General tab
of the Properties view for a 3D graph, PowerBuilder launches the
DirectX installer. If you opt out of the installation, the Render3D
property is ignored. End users of PowerBuilder applications must
also have the DirectX runtime installed on their computers to view
the DirectX graph styles. You can download a redistributable package containing
the DirectX runtime from the <A HREF="http://www.microsoft.com/downloads/details.aspx?FamilyId=822640AB-0983-4C41-9C70-632F6F42C557&amp;displaylang=en">Microsoft Web site</A></p>
<A NAME="TI6871"></A><p>For computers with older graphics drivers, you can check whether
DirectX is supported by running <i>dxdiag.exe</i>.
This file is typically installed in the <i>Windows\System32</i> directory.
The Display tab of the DirectX Diagnostic Tool that opens when you
run <i>dxdiag.exe</i> indicates whether Direct3D is
enabled.</p>
<A NAME="TI6872"></A><h4>AJAX extensions</h4>
<A NAME="TI6873"></A><p>PowerBuilder uses AJAX
(Asynchronous JavaScript and XML) update functionality for Web Forms
applications. With ASP.NET AJAX, the page is updated by refreshing
individual regions of the page asynchronously.</p>
<A NAME="TI6874"></A><p>Although PowerBuilder .NET Web Forms and .NET Web Service
component targets work with .NET Framework 3.5, they do not use
the version of AJAX that installs with .NET Framework 3.5. You must
install AJAX Extensions version 1.0 (build 61025.0) for these .NET
target types.</p>
<A NAME="TI6875"></A><p>Because PowerBuilder uses the AJAX update feature by default,
AJAX extensions are required for Web Forms applications on all development
and deployment machines. You can download and install the Microsoft
ASP.NET AJAX Extensions version 1.0 from <A HREF="http://www.asp.net/ajax/downloads/archive">the ASP.NET Web site</A>
.</p>
<A NAME="BABCHDDC"></A><h2>Sun Microsystems files</h2>
<A NAME="TI6876"></A><p>The Java Runtime Environment (JRE) is required for EJB clients,
JDBC connections, and saving as PDF using XSL-FO. For a copy of
third-party terms and conditions for the JRE, see the free
download terms document.The JRE can be downloaded from the <A HREF="http://java.sun.com/javase/downloads/index.jsp">Sun Developer Network</A>
.</p>
<A NAME="BABDFAFJ"></A><h2>Software used for SOAP clients for Web services</h2>
<A NAME="TI6877"></A><p>PowerBuilder includes the EasySoap++ library
in executable form in <i>EasySoap115.dll</i>, which
is dynamically linked to <i>PBSoapClient115.pbx</i>.
The EasySoap++ library and its use are covered
by the GNU Lesser General Public License (LGPL). For a copy of this
license, see the free download terms document. You may distribute
the EasySoap++ library to third parties subject
to the terms and conditions of the LGPL. Please read the LGPL prior
to any such distribution.</p>
<A NAME="TI6878"></A><p>The complete machine-readable source code for the EasySoap++ library
is provided in the <i>EasySoap.zip</i> file in the <i>Support\WSExtn</i> folder
on the DVD. In addition, the object code and Microsoft Visual C++ project
file for the <i>PBSoapClient115.pbx</i> are provided
in the <i>soapclient.zip</i> file in the same directory. </p>
<A NAME="TI6879"></A><p>These files are provided under the terms of the LGPL so that
you can modify the EasySoap++ library and then
relink to produce a modified <i>EasySoap115.dll</i>.
You can also relink <i>PBSoapClient115.pbx</i> with
the modified EasySoap++ import library. According
to the terms of the LPGL, it is understood that you will not necessarily
be able to recompile <i>PBSoapClient115.pbx</i> to
use the definitions you have modified in the EasySoap++ library. </p>
<A NAME="TI6880"></A><p>Follow the instructions in the <i>Readme.txt</i> file
in the <i>soapclient.zip</i> file to build <i>PBSoapClient115.pbx</i>.</p>
<A NAME="TI6881"></A><h2>Telerik controls for Web Forms applications</h2>
<A NAME="TI6882"></A><p>PowerBuilder installs Telerik RadControls for ASP.NET and
deploys these controls to the ASP.NET server with your Web Forms
applications. RadControls provide enhanced functionality for Web
Forms toolbars and menus, DatePicker and MonthCalendar controls,
and TreeView controls. End users of Web Forms applications do not
need to install RadControls on their computers.</p>

